Method and system for automatic data aggregation

ABSTRACT

A system, for automatic data aggregation, may include a communications module to access an electronic form, a detector to detect a workflow indication associated with the electronic form. The system further comprises and an aggregator. The aggregator may be configured to associate electronic form data with an aggregate package in response to the detected workflow indication. The electronic form data may be presented in the aggregate package as a separate record.

TECHNICAL FIELD

This application relates to a method and system for automatic dataaggregation.

BACKGROUND

The approaches described in this section could be pursued, but are notnecessarily approaches that have been previously conceived or pursued.Therefore, unless otherwise indicated herein, the approaches describedin this section are not prior art to the claims in this application andare not admitted to be prior art by inclusion in this section.

Portable Document Format (PDF) is a standard for a secure and reliabledistribution and exchange of electronic documents and forms. PDF is afile format that preserves fonts, images, graphics, and layout of asource document, regardless of the application and platform used tocreate it. Adobe® PDF files are compact and complete, and can be shared,viewed, and printed by anyone with free Adobe Reader® software.

The data contained in several homogenous PDF forms may be aggregated byexporting it to a spreadsheet. For example, a separate row in aspreadsheet may store the field's values of the original PDF form. Aseparate column may store values associated with a particular field ofthe original PDF forms. The data from several PDF forms may also beexported into a database, where a database record may represent aseparate PDF form.

In order to aggregate data from a plurality of PDF forms into aspreadsheet or to import it into a database, a user may need to firstmake a determination of whether any given electronic form contains datathat is appropriate for being transferred into a target spreadsheet or atarget database file.

BRIEF DESCRIPTION OF DRAWINGS

Embodiments are illustrated by way of example and not limitation in thefigures of the accompanying drawings, in which like references indicatesimilar elements and in which:

FIG. 1 is a block diagram showing an architecture within which a methodand system to aggregate data from several electronic forms into aportable format may be implemented, in accordance with an exampleembodiment;

FIG. 2 is a block diagram illustrating a system, in accordance with anexample embodiment, to aggregate a set of collected electronic formsinto one aggregate package;

FIG. 3 is a flow chart illustrating a method to aggregate a set ofcollected electronic forms, in accordance with an example embodiment;

FIG. 4 is a flow chart illustrating a method to add data associated withan electronic form into an aggregate package utilizing workflowmetadata, in accordance with an example embodiment;

FIG. 5 illustrates an original electronic form, in accordance with anexample embodiment; and

FIG. 6 illustrates a summary sheet, in accordance with an exampleembodiment; and

FIG. 7 illustrates a diagrammatic representation of a machine in theexample form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

In an example embodiment, a method and system are provided to aggregatedata from several original electronic forms (e.g., several instances ofan original electronic form) into a single file container. It will benoted, that, for the purposes of this description, the terms “form” and“electronic form” may be used interchangeably. The resulting aggregatepackage (e.g., a single PDF file or a plurality of associated files) mayinclude an aggregate representation of field data associated with theseveral original electronic forms, such that field data associated withone electronic form is presented to a viewer as one record, e.g., in atabular format. The aggregate representation of field data associatedwith the several original electronic forms may be in a form of a summarysheet. Furthermore, the visually rich representation of an originalelectronic form may be preserved by saving characterizations of theoriginal electronic form as part of the aggregate package. In oneexample embodiment, where an aggregate package is a PDF file, thecharacterizations of an original electronic form may be saved as anattachment associated with the PDF file.

In an example embodiment, a workflow of an electronic form begins by an“initiator” (e.g., a person or an automated process) sending an originalelectronic form (e.g., a blank electronic form) to people who need tofill it out. The original electronic form may include informationindicating that all instances of the original electronic form areassociated with a particular workflow. In one example embodiment, suchan indication may be represented by metadata associated with anelectronic form. When each filled-in original form instance is returnedto the initiator and opened utilizing an associated viewer application,the metadata may be discovered and the user may be prompted to indicatewhether this form instance should be added to an aggregate package. Anexample aggregate package, sometimes referred to as a dataset or anaggregate dataset, may include a container file that serves as acontainer for each of the aggregated form instances, which may beinserted as attachments. An initiator may be provided with a visualdisplay that shows a tabulated view of all form instances in thedataset, e.g., a tabulated view or a list view. A user may be permittedto open an original form instance for inspection from within thetabulated view by performing a predetermined control action. A controlaction may be, for example, a user action such as a single or a doubleclick on a row representing field data of a particular instance of theoriginal form. In an example embodiment, a control button may beprovided to permit a user to view a form instance associated with aselected row. A user may also be permitted to remove any form instancefrom the dataset by deleting the corresponding attachment.

Thus, the system, in an example embodiment, may be configured toaggregate data associated with various collected instances of theoriginal form and to render the aggregated form data in a tabular format(or some other format) or in an aggregated or collected manner, and alsoto permit a user to view a selected instance of the original form in itsoriginal visually rich format. Furthermore, the system may be configuredto permit a user to remove a particular instance of the original formfrom the aggregate package, such that its form field data presented inan aggregated or collected manner, as well as the associated instance ofthe original form, are removed from the aggregate package. In an exampleembodiment, the view and remove operations may be performed in a dragand drop manner. An example architecture of a system to aggregate datais illustrated in FIG. 1.

FIG. 1 shows an architecture 100, within which a method and system toaggregate data from several electronic forms into a portable format maybe implemented, in accordance with an example embodiment. In the contextof the architecture 100, in an example embodiment, multiple instances110 of an original electronic form are received and processed by aportable aggregation logic 120. The portable aggregation logic 120 maybe configured to access an original form 110 and detect that theoriginal form 110 includes an associated workflow metadata indicatingthat the original form 110 may be aggregated with other forms or forminstances associated with the same workflow. Workflow metadata, in oneembodiment, may include a workflow identifier so as to enableassociation of the form with a workflow description. The portableaggregation logic 120 may also be configured to determine a location ofan existing aggregate package 130 associated with the workflow andselectively add the form data into the aggregate package 130. It will benoted that in an example embodiment, portable aggregation logic 120 maybe configured to determine that a target aggregate package for aparticular workflow does not exist and, in response to thisdetermination, generate a target aggregate package (e.g., aggregatepackage 130).

Thus, the processing by the portable aggregation logic 120, in anexample embodiment, may result in a newly generated aggregate package130 or in an aggregate package 130, where data associated with one ormore original forms 110 has been selectively added. The aggregatepackage 130, in an example embodiment, comprises field data 132 obtainedfrom one or more original forms 110. The field data in the aggregatepackage 130 may be presented to a user in a tabular format, e.g., wherea particular row corresponds to field data from a particular originalform 110. In an example embodiment, where the forms 110 are differentinstances of a single original form, a particular column in the tabularrepresentation of form field data in the aggregate package maycorrespond to values associated with a particular field in the originalform.

The aggregate package 130, in an example embodiment, further comprisesoriginal forms 110 saved as attachments 134. A system for portable dataaggregation may be configured, in an example embodiment, to receive acontrol action associated with a row in a tabular representationcorresponding to a particular original form or a particular originalform instance. The system may then display a representation of theassociated original form in a visually rich original format. A controlaction may be, for example, a click, an actuating of a control button,etc.

It will be noted that, as mentioned above, the portable data aggregation120 may be performed on a multiple instances of a particular originalform, as well as on a plurality of heterogeneous electronic forms, wheredifferent electronic forms received by the portable data aggregationlogic 120 may have different form fields, different presentationcharacteristics, as well as different form field values. An examplesystem to aggregate data from a plurality of electronic form instancesis described with reference to FIG. 2.

FIG. 2 shows a block diagram illustrating a system 200, in accordancewith an example embodiment, to aggregate a set of collected electronicforms into one aggregate package. The system 200, in an exampleembodiment, comprises a communications module 220, a field dataextractor 230, an aggregator 240 and a characterization module 250. Thecommunications module 220 may be configured to receive multipleelectronic forms. The received electronic forms may be, in one exampleembodiment, multiple instances of an original electronic form. Inanother example embodiment, the received forms may be instances ofdifferent electronic forms.

The communications module 220 may be configured to cooperate with thefield data extractor 230, which, in turn, may be configured to extractfield data from each one of the received electronic forms and to providethe extracted data to the aggregator 240. The aggregator 240 may beconfigured to add the extracted field data into an aggregate package.The aggregator 240 may also be configured to generate a tabularrepresentation of the extracted field data.

The characterization module 250 may be configured to add, into anaggregate package, a characterization of a form received by thecommunications module 220 and added by the aggregator 240. In oneexample embodiment, the characterization of a form received by thecommunications module 220 may be added into an aggregate package bysaving the received electronic form as an attachment associated theaggregate package. In another embodiment, the characterization may beassociated with an aggregate package, for example by association dataincluded within the application package which points to a storagelocation at which the characterization is stored. The savedcharacterization of a form may be utilized to preserve visualpresentation of the received electronic form.

The system 200, in an example embodiment, may further include aresponder 260 and a remover 270. The responder 260 may be configured topermit viewing of an original representation of a received form from theaggregate package. The remover 270 may be configured to permit removingall representations of a particular electronic form from the aggregatepackage.

As mentioned above, a system for portable data aggregation may beconfigured to detect metadata within an electronic form indicating thatthe electronic form is associated with a particular workflow. Thus, thesystem 200 may include a detector 280 to detect automatically that anelectronic form is part of a particular workflow. In one exampleembodiment, the detector 280 may be configured to perform the detectingof whether an electronic form is part of a particular workflow after theelectronic form is opened for viewing by an associated application. Inan alternative embodiment, the detector 280 may be configured toperiodically scan a predetermined destination (e.g., a particular folderor directory, an inbox associated with initiator's electronic mailclient, etc), notify the initiator of any newly detected electronicforms associated with a workflow, and then automatically add theelectronic forms associated with a workflow to a determined destinationaggregate package. Various operations performed by the system 200,according to an example embodiment, may be described with reference toFIG. 3.

FIG. 3 is a flow chart illustrating a method 300 to aggregate a set ofcollected electronic forms, in accordance with an example embodiment.The method 300 may be performed by processing logic that may comprisehardware (e.g., dedicated logic, programmable logic, microcode, etc.),software (such as run on a general purpose computer system or adedicated machine), or a combination of both.

As shown in FIG. 3, the method 300 commences with the communicationsmodule 220 from FIG. 2 receiving one or more electronic forms atoperation 302. At operation 304, the field data extractor 230 extractsthe field data from the received electronic forms, and the aggregator240 aggregates the extracted field data to generate an aggregated format operation 306. The aggregator 240 may then pass control to thecharacterization module 250.

At operation 308, the characterization module 250 may save the receivedelectronic forms as attachments associated wit the aggregated form. Theresulting aggregated form (e.g., in an example embodiment of a summarysheet as discussed below) may be displayed to a user on demand, atoperation 310. As mentioned above, the system 200 may include a detector280 to detect automatically that an electronic form is part of aworkflow. A method utilizing workflow metadata is discussed withreference to FIG. 4.

FIG. 4 is a flow chart illustrating a method 400 to add data associatedwith an electronic form into an aggregate package utilizing workflowmetadata, in accordance with an example embodiment. The method 400 maybe performed by processing logic that may comprise hardware (e.g.,dedicated logic, programmable logic, microcode, etc.), software (such asrun on a general purpose computer system or a dedicated machine), or acombination of both. In one example embodiment, the method 400 may beperformed by the various modules discussed above with reference to FIG.2. Each of these modules may comprise processing logic.

As mentioned above, a form's workflow may include an initiator sending ablank form to multiple recipients and then receiving filled out versionsof the form from those recipients. The original blank form may includemetadata (e.g., workflow metadata) identifying instances of the originalform as associated with a particular workflow and also identifying adestination aggregate package, should a form instance be aggregated intoa dataset. The workflow metadata may be inserted into a form in responseto an initiator requesting that the form is distributed to multiplerecipients. Each received filled out form, in an example embodiment, maybe an instance of an original blank form that was sent out.

When the filled out forms arrive, e.g., to the initiator's mail clientinbox, a system for portable data aggregation (e.g., the system 200 ofFIG. 2) may detect embedded workflow metadata and determine a potentialdestination for any data associated with the received forms. As shown inFIG. 4, the method 400 commences with the communications module 220accessing an electronic form at operation 402. At operation 404, thedetector 280 of FIG. 2 detects workflow metadata being present in theform. The detected metadata may also identify a destination, e.g., atarget aggregate package, for data associated with the form. In oneexample embodiment, the system for portable data aggregation 200 maytrigger a prompt requesting instructions regarding whether any dataassociated with the form is to be added into the target aggregatepackage (operation 406).

If it is determined, at operation 408, that the form data (e.g., thefield data, the characterization of the form, or any other dataassociated with the form) is to be included in a target aggregatepackage, it is next determined, at operation 410, whether the targetaggregate package already exists. If the target aggregate package doesnot exist, the target aggregate package is generated at operation 412.Otherwise, the method 400 proceeds to operation 414 to add dataassociated with the electronic form into the aggregated package.

An example original form that may be processed utilizing methods 300 and400 is discussed with reference to FIG. 5.

FIG. 5 illustrates an original electronic form 500, in accordance withan example embodiment. The electronic form 500, entitled “HolidayVacation Form,” comprises a plurality of data fields that may receivefield values in response to a user input. In the example “HolidayVacation Form” 500, a “Name” field 502 has an associated field value“Benjamin Martin” 504. A “Street Address” field 506 has an associatedfield value “19121 Evelyn Avenue” 508. A “City” field 510 has anassociated field value “Sunnyvale” 512. A “ZIP” field 514 has anassociated field value “94086” 520. Finally, a “Daytime Phone” field 522has an associated field value “408-376-5400” 524.

As mentioned above, an electronic form, e.g., the “Holiday VacationForm” 500, may have embedded metadata such that an instance of the formmay be identified by the system as part of a workflow. In an exampleembodiment, if an electronic form is identified by the system as part ofa specific workflow, the system may selectively (e.g., after prompting auser for instructions regarding aggregating) add the electronic formdata into an aggregate package, e.g., as shown in FIG. 6.

An example summary sheet 600 is illustrated in FIG. 6. As shown in FIG.6, the field values from the “Holiday Vacation Form” 500 appear in asingle row 610 of the summary sheet 600. A catalog identificationassociated with each of the electronic forms aggregated into the summarysheet 600 may be provided in an “ID” column 620.

It will be noted that, although some example embodiments of theinvention have been described in the context of PDF electronic forms,the techniques herein may be utilized advantageously with a variety ofdata presentation formats that are suitable for providing electronicforms to users. In one example embodiment, an aggregate package may beimplemented as an extensible Markup Language (XML) file.

As discussed above, the system to aggregate a set of collectedelectronic forms into an aggregate package may receive electronic formsfrom users who filled out a distributed form. In one example embodiment,the system may be configured to receive just field data associated witha filled out electronic form (e.g. in the XML format), as opposed to thewhole completed form (e.g. a PDF file). The returned XML file may thenbe associated with an appropriate aggregate package. The XML data may beincluded, in one embodiment, into the aggregate package as one of therecords in the tabulated view. When the system detects a user's requestto display a complete form for that particular record, the system mayopen a copy of a blank form, import the XML data into the blank form,and display the resulting form to the user.

FIG. 7 shows a diagrammatic representation of a machine in the exampleelectronic form of a computer system 700 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In various embodiments,the machine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a portable music player (e.g., a portablehard drive audio device such as an “Moving Picture Experts Group (MPEG)Layer 3” (MP3) player), a web appliance, a network router, switch orbridge, or any machine capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

The example computer system 700 includes a processor 702 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 704 and a static memory 706, which communicate witheach other via a bus 708. The computer system 700 may further include avideo display unit 710 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 700 also includes analphanumeric input device 712 (e.g., a keyboard), a user interface (UI)navigation device 714 (e.g., a mouse), a disk drive unit 716, a signalgeneration device 718 (e.g., a speaker) and a network interface device720.

The disk drive unit 716 includes a machine-readable medium 722 on whichis stored one or more sets of instructions and data structures (e.g.,software 724) embodying or utilized by any one or more of themethodologies or functions described herein. The software 724 may alsoreside, completely or at least partially, within the main memory 704and/or within the processor 702 during execution thereof by the computersystem 700, the main memory 704 and the processor 702 also constitutingmachine-readable media.

The software 724 may further be transmitted or received over a network726 via the network interface device 720 utilizing any one of a numberof well-known transfer protocols (e.g., Hyper Text Transfer Protocol(HTTP)).

While the machine-readable medium 722 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present invention, or that is capable of storing,encoding or carrying data structures utilized by or associated with sucha set of instructions. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, solid-statememories, optical and magnetic media, and carrier wave signals. Suchmedium may also include, without limitation, hard disks, floppy disks,flash memory cards, digital video disks, random access memory (RAMs),read only memory (ROMs), and the like.

The embodiments described herein may be implemented in an operatingenvironment comprising software installed on a computer, in hardware, orin a combination of software and hardware.

Thus, a method and system for portable data aggregation have beendescribed. Although embodiments have been described with reference tospecific example embodiments, it will be evident that variousmodifications and changes may be made to these embodiments withoutdeparting from the broader spirit and scope of the invention.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

1. A system comprising: a communications module to access an electronicform; a detector to detect an indication associated with the electronicform, the electronic form comprising field data; and an aggregator toassociate the field data with an aggregate package in response to thedetected indication, the field data being presented in the aggregatepackage as a separate record.
 2. The system of claim 1, wherein thedetector is to scan periodically a file storage location for theindication.
 3. The system of claim 1, wherein the detector is to requestinstructions regarding associating the field data with the aggregatepackage in response to the detected indication.
 4. The system of claim1, wherein the aggregator is to: generate the aggregate package inresponse to the detecting of the indication and responsive to adetermination that the aggregate package does not exist.
 5. The systemof claim 1, wherein the aggregator is to generate a catalogidentification for the electronic form, the catalog identification toidentify the electronic form associated with the field data in theaggregate package.
 6. The system of claim 1, wherein the aggregatepackage is an extensible Markup Language (XML) data file.
 7. The systemof claim 1, wherein the aggregate package comprises a plurality offiles.
 8. The system of claim 1, further comprising a characterizationmodule to associate a characterization of the electronic form with theaggregate package to preserve visual presentation of the electronicform.
 9. The system of claim 8, further comprising a responder to:receive a control action associated with the separate record; anddisplay a representation of the electronic form in response to thecontrol action utilizing the characterization of the electronic form.10. The system of claim 9, wherein the control action is clicking on theseparate record.
 11. The system of claim 9, further comprising a removerto: receive a remove control action associated with the separate record;and remove the field data and the characterization of the electronicform from the aggregate package in response to the remove controlaction.
 12. The system of claim 1, wherein the electronic form is in aPortable Document Format (PDF).
 13. The system of claim 1, wherein theindication comprises workflow metadata associated with the electronicform.
 12. A method comprising: accessing an electronic form; detecting aworkflow indication associated with the electronic form; adding dataassociated with the electronic form into an aggregate package inresponse to the detecting of the workflow indication; and presenting thedata associated with the electronic in the aggregate package as anaggregate representation of the field data.
 13. The method of claim 12,wherein the detecting of the workflow indication comprises scanningperiodically a file storage location for the indication.
 14. The methodof claim 12, further comprising requesting instructions regardingassociating the data associated with the electronic form with theaggregate package in response to the detecting of the workflowindication.
 15. The method of claim 12, wherein the associating of thedata associated with the electronic form with an aggregate packagecomprises: determining that the aggregate package does not exist; andgenerating the aggregate package.
 16. The method of claim 12, whereinthe associating of the data associated with the electronic form with anaggregate package comprises generating a catalog identification for theelectronic form, the catalog identification to identify the dataassociated with the electronic form in the aggregate package.
 17. Themethod of claim 12, wherein the adding of the data associated with theelectronic form into an aggregate package comprises associatingcharacterization of the electronic form with the aggregate package topreserve visual presentation of the electronic form.
 18. The method ofclaim 17, further comprising: receiving a control action associated withan aggregate representation of the data associated with the electronicform in the aggregate package; and displaying a representation of theelectronic form in response to the control action utilizing thecharacterization of the electronic form.
 19. The method of claim 12,wherein the workflow indication comprises metadata associated with theelectronic form.
 20. A machine-readable medium having instruction datato cause a machine to: detect workflow metadata associated with anelectronic form, the electronic form comprising field data; receiveconfirmation that the electronic form is to be associated with anaggregate package; and associate the field data with the aggregatepackage in response to the confirmation, the field data associated beingpresented in the aggregate package as a separate record.
 21. A systemcomprising: means for detecting a workflow indication associated with anelectronic form, the electronic form comprising field data; means forassociating the field data with the aggregate package in response to theworkflow indication; and means for presenting the field data in theaggregate package as a separate record.